Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a251b12407ecbe3fd3990fad185d8e99f072412fb64da53cd15ce4281628486c

Tx prefix hash: 78c34e5c4596241adaa4da0519865007c6cb139b13ae5c5cf721c2de8727c71f
Tx public key: 3d4c104c5196371f0f9befd975b83b8367bb9abd3c1f2e22501882fc01002a72
Timestamp: 1578950870 Timestamp [UCT]: 2020-01-13 21:27:50 Age [y:d:h:m:s]: 04:312:03:34:27
Block: 44976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1112513 RingCT/type: yes/0
Extra: 013d4c104c5196371f0f9befd975b83b8367bb9abd3c1f2e22501882fc01002a720211000000078a2ee0d9000000000000000000

1 output(s) for total of 435.488490867000 dcy

stealth address amount amount idx
00: ea17a1c0cb4c76cbd1022a164f3c3e8976da86025fdf5eddc195c6662ec0acdf 435.488490867000 82022 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": 44986, "vin": [ { "gen": { "height": 44976 } } ], "vout": [ { "amount": 435488490867, "target": { "key": "ea17a1c0cb4c76cbd1022a164f3c3e8976da86025fdf5eddc195c6662ec0acdf" } } ], "extra": [ 1, 61, 76, 16, 76, 81, 150, 55, 31, 15, 155, 239, 217, 117, 184, 59, 131, 103, 187, 154, 189, 60, 31, 46, 34, 80, 24, 130, 252, 1, 0, 42, 114, 2, 17, 0, 0, 0, 7, 138, 46, 224, 217, 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