Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0957640fbb0124c31b934566b98e53ae767cea563a152552732d96866ca99e33

Tx prefix hash: 1381a29831b0ee0e58f7fdc6d2cc72eea87770e6c8c6d9764e35a65b82195aec
Tx public key: 439c78bc41a641642a50cd162b3e1117d7f5bd8c249b3dbb7bec5180e81f980e
Timestamp: 1730771497 Timestamp [UCT]: 2024-11-05 01:51:37 Age [y:d:h:m:s]: 00:064:15:43:12
Block: 1146764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46265 RingCT/type: yes/0
Extra: 01439c78bc41a641642a50cd162b3e1117d7f5bd8c249b3dbb7bec5180e81f980e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b2c7f941dc8dd824e8ed4f97dae1efa542853a178fca3a404b64be3d6694507 0.600000000000 1631455 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": 1146774, "vin": [ { "gen": { "height": 1146764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b2c7f941dc8dd824e8ed4f97dae1efa542853a178fca3a404b64be3d6694507" } } ], "extra": [ 1, 67, 156, 120, 188, 65, 166, 65, 100, 42, 80, 205, 22, 43, 62, 17, 23, 215, 245, 189, 140, 36, 155, 61, 187, 123, 236, 81, 128, 232, 31, 152, 14, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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