Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 503c2ae3dfa2dc8f27062990df0392c32b9e3a478266899ddae9bf83ad4f95a8

Tx prefix hash: 080852b3dca6c56042c060c7cc714e753a0f131e92355b0dbdf818c4d82cc996
Tx public key: 6c1814449e5ced8e39618a8718c53f312f2bb4bc44ef2a4fad4cc6b864ae53eb
Timestamp: 1707670444 Timestamp [UCT]: 2024-02-11 16:54:04 Age [y:d:h:m:s]: 00:354:01:50:59
Block: 955337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253204 RingCT/type: yes/0
Extra: 016c1814449e5ced8e39618a8718c53f312f2bb4bc44ef2a4fad4cc6b864ae53eb0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27e3d4eb4e5163d5cc9eb8a8eba3e804555d4e427964e0e30015c1b6e1fcb0ba 0.600000000000 1414623 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": 955347, "vin": [ { "gen": { "height": 955337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27e3d4eb4e5163d5cc9eb8a8eba3e804555d4e427964e0e30015c1b6e1fcb0ba" } } ], "extra": [ 1, 108, 24, 20, 68, 158, 92, 237, 142, 57, 97, 138, 135, 24, 197, 63, 49, 47, 43, 180, 188, 68, 239, 42, 79, 173, 76, 198, 184, 100, 174, 83, 235, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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