Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3f0be8d51950215f9b0c6542c7c15576d7b4687fe6938d24aa09ad247271eaa

Tx prefix hash: 519379e6139120dc134a56b50951427fd81f1fa0fa660d3919e525a8437918f2
Tx public key: 300e925e16270cdd19c3daa18db39b6322aacb8e3f5a258786249ea8cbbfda28
Timestamp: 1711685619 Timestamp [UCT]: 2024-03-29 04:13:39 Age [y:d:h:m:s]: 00:361:21:42:06
Block: 988637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258727 RingCT/type: yes/0
Extra: 01300e925e16270cdd19c3daa18db39b6322aacb8e3f5a258786249ea8cbbfda280211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c228b3aa52980816fdf061d1f5cc9da219bbd9a62f58ada0f2503837ae6ed040 0.600000000000 1448918 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": 988647, "vin": [ { "gen": { "height": 988637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c228b3aa52980816fdf061d1f5cc9da219bbd9a62f58ada0f2503837ae6ed040" } } ], "extra": [ 1, 48, 14, 146, 94, 22, 39, 12, 221, 25, 195, 218, 161, 141, 179, 155, 99, 34, 170, 203, 142, 63, 90, 37, 135, 134, 36, 158, 168, 203, 191, 218, 40, 2, 17, 0, 0, 0, 6, 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