Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc8cdd6c913bced7e6a0060e76c77f2ce8bdfb8694e19641e2808f6632dfd8c0

Tx prefix hash: eebdb7ff3fcd216833c06e7e0fb942b1b336b7d10710b7c39d9510102a9d4fc3
Tx public key: b1abe2c9d3b656ad27030143cac235c77661f6cbc82fa37eeec086b55d5dfa8d
Timestamp: 1689557858 Timestamp [UCT]: 2023-07-17 01:37:38 Age [y:d:h:m:s]: 01:302:12:39:55
Block: 805438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477365 RingCT/type: yes/0
Extra: 01b1abe2c9d3b656ad27030143cac235c77661f6cbc82fa37eeec086b55d5dfa8d021100000001faf35c9c000000000000000000

1 output(s) for total of 1.315981169000 dcy

stealth address amount amount idx
00: 2baa4ebf8767bded13a94b9c4ef5f97c4daecb29a5fce5ab6f1e837fd46fc3df 1.315981169000 1256665 of 0

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": 805448, "vin": [ { "gen": { "height": 805438 } } ], "vout": [ { "amount": 1315981169, "target": { "key": "2baa4ebf8767bded13a94b9c4ef5f97c4daecb29a5fce5ab6f1e837fd46fc3df" } } ], "extra": [ 1, 177, 171, 226, 201, 211, 182, 86, 173, 39, 3, 1, 67, 202, 194, 53, 199, 118, 97, 246, 203, 200, 47, 163, 126, 238, 192, 134, 181, 93, 93, 250, 141, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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