Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 8cecb0330adc6478d39bf31e4573559207ad2b97cd6a158d1a87fcff3ae5e86b

Tx prefix hash: 7a349e5af7b7794233d4d83833cfd5f567a8bdd48eb1e2de964043755372fbff
Tx public key: 93ba7893b743425a546d38bb4da9efc79b005a9bbc35f1e4b7aaa6b91f41e56c
Timestamp: 1699423246 Timestamp [UCT]: 2023-11-08 06:00:46 Age [y:d:h:m:s]: 01:108:05:34:19
Block: 886967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338503 RingCT/type: yes/0
Extra: 0193ba7893b743425a546d38bb4da9efc79b005a9bbc35f1e4b7aaa6b91f41e56c021100000001679a8a81000000000000000000

1 output(s) for total of 0.706496694000 dcy

stealth address amount amount idx
00: 2996c1d727eb92c7a8f9d21a427ff77b171d460a895e0d8768fc40684bd14642 0.706496694000 1342814 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 886977, "vin": [ { "gen": { "height": 886967 } } ], "vout": [ { "amount": 706496694, "target": { "key": "2996c1d727eb92c7a8f9d21a427ff77b171d460a895e0d8768fc40684bd14642" } } ], "extra": [ 1, 147, 186, 120, 147, 183, 67, 66, 90, 84, 109, 56, 187, 77, 169, 239, 199, 155, 0, 90, 155, 188, 53, 241, 228, 183, 170, 166, 185, 31, 65, 229, 108, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8