Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2611ad5397774a1d07de68aaa6e288b2087f6158b57ed73aac6585da12685a35

Tx prefix hash: 95c7ccf291be455468621ba1ec9e6ae3a902670a7ea7f65407b0a8a36342a36a
Tx public key: bd8c98031a5eca65cc22f6b3d47e8e09b10c9e259017049a2f16cb892ea576cb
Timestamp: 1715044376 Timestamp [UCT]: 2024-05-07 01:12:56 Age [y:d:h:m:s]: 00:250:06:29:33
Block: 1016483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179111 RingCT/type: yes/0
Extra: 01bd8c98031a5eca65cc22f6b3d47e8e09b10c9e259017049a2f16cb892ea576cb0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ea6916038c60fe45f2ca95be7847a415e3c939dde2534dafadce62db0f8d187 0.600000000000 1480076 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": 1016493, "vin": [ { "gen": { "height": 1016483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ea6916038c60fe45f2ca95be7847a415e3c939dde2534dafadce62db0f8d187" } } ], "extra": [ 1, 189, 140, 152, 3, 26, 94, 202, 101, 204, 34, 246, 179, 212, 126, 142, 9, 177, 12, 158, 37, 144, 23, 4, 154, 47, 22, 203, 137, 46, 165, 118, 203, 2, 17, 0, 0, 0, 1, 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