Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fad74c7e08dbaafa315a537ef13e500037d9f4a77f71196c0400fb8c19e93ef7

Tx prefix hash: 6564b34e6dc3a025287c24e5a45b35f3b9229bbdc6809261a8ba309f7dac6cff
Tx public key: 8ceff8d9158dcc0e41a699b0e54c0b0796b33db9140ab7732f37f59db57e3cf1
Timestamp: 1731767447 Timestamp [UCT]: 2024-11-16 14:30:47 Age [y:d:h:m:s]: 00:125:02:32:32
Block: 1155019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89232 RingCT/type: yes/0
Extra: 018ceff8d9158dcc0e41a699b0e54c0b0796b33db9140ab7732f37f59db57e3cf1021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87ee16b12e04e9bb6dc85e1fed87b5c94f7a9af33ce0e8ac7cf9149c2feb27ab 0.600000000000 1640632 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": 1155029, "vin": [ { "gen": { "height": 1155019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87ee16b12e04e9bb6dc85e1fed87b5c94f7a9af33ce0e8ac7cf9149c2feb27ab" } } ], "extra": [ 1, 140, 239, 248, 217, 21, 141, 204, 14, 65, 166, 153, 176, 229, 76, 11, 7, 150, 179, 61, 185, 20, 10, 183, 115, 47, 55, 245, 157, 181, 126, 60, 241, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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