Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 182f82e9d913dd5f54bc24a38b75ab6b591bf3056dd3738707233d135a7279b6

Tx prefix hash: 5e63395ca134804e9ddc8d959aa3065fb08797125005bddf532c912846dedb39
Tx public key: 89ce768b4fb5e5a9eabcf1845d0a2800b10cd9de443fda4b74bf7bac272dc529
Timestamp: 1729067695 Timestamp [UCT]: 2024-10-16 08:34:55 Age [y:d:h:m:s]: 00:148:14:01:48
Block: 1132740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105968 RingCT/type: yes/0
Extra: 0189ce768b4fb5e5a9eabcf1845d0a2800b10cd9de443fda4b74bf7bac272dc5290211000000053cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8f6b3dce7c1fcb2d24465d13c35f7cf4f23ca50dd08b2ef5ce688ec1bb9ae1e 0.600000000000 1615723 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": 1132750, "vin": [ { "gen": { "height": 1132740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8f6b3dce7c1fcb2d24465d13c35f7cf4f23ca50dd08b2ef5ce688ec1bb9ae1e" } } ], "extra": [ 1, 137, 206, 118, 139, 79, 181, 229, 169, 234, 188, 241, 132, 93, 10, 40, 0, 177, 12, 217, 222, 68, 63, 218, 75, 116, 191, 123, 172, 39, 45, 197, 41, 2, 17, 0, 0, 0, 5, 60, 208, 252, 6, 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