Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd793679c1f90d16d134b77da45952d12b878f1c4304c6cad6c32c5889ff5c32

Tx prefix hash: 8000d286d0d766a84ee28c04065a7d71f3a8432fe4a4b2ac9650c70089c11d03
Tx public key: e5553320d623a66ee2efa5a4926f0eaf4917e0ddd77b6cde1b6e691b417e70a7
Timestamp: 1711115276 Timestamp [UCT]: 2024-03-22 13:47:56 Age [y:d:h:m:s]: 00:236:20:22:39
Block: 983921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169538 RingCT/type: yes/0
Extra: 01e5553320d623a66ee2efa5a4926f0eaf4917e0ddd77b6cde1b6e691b417e70a70211000000140011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 765856e21ac1bda33280558099c22ecd0157b56eb26e3cb8edf5879d82222825 0.600000000000 1444074 of 15

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": 983931, "vin": [ { "gen": { "height": 983921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "765856e21ac1bda33280558099c22ecd0157b56eb26e3cb8edf5879d82222825" } } ], "extra": [ 1, 229, 85, 51, 32, 214, 35, 166, 110, 226, 239, 165, 164, 146, 111, 14, 175, 73, 23, 224, 221, 215, 123, 108, 222, 27, 110, 105, 27, 65, 126, 112, 167, 2, 17, 0, 0, 0, 20, 0, 17, 5, 91, 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