Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba5b05bc68ea5dab4aa8128d1ef2d8e212fdcb10e7c5d86cd053d35116582a0c

Tx prefix hash: 0e5e6616b61d28d4e7f7d465988c79ef0d49f7014002766bd8ebaf7ff58e1409
Tx public key: ca7fa3ebb588408934e9e5ab225736cc89486cbe3da15e1dcac567474f4f9cf0
Timestamp: 1700750881 Timestamp [UCT]: 2023-11-23 14:48:01 Age [y:d:h:m:s]: 01:133:05:13:04
Block: 897968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356372 RingCT/type: yes/0
Extra: 01ca7fa3ebb588408934e9e5ab225736cc89486cbe3da15e1dcac567474f4f9cf002110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.649619777000 dcy

stealth address amount amount idx
00: 47f33675e43ed382e78c21cd7bd1e0e106c6df7d808e5c0b3506c74abf9d21eb 0.649619777000 1354369 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": 897978, "vin": [ { "gen": { "height": 897968 } } ], "vout": [ { "amount": 649619777, "target": { "key": "47f33675e43ed382e78c21cd7bd1e0e106c6df7d808e5c0b3506c74abf9d21eb" } } ], "extra": [ 1, 202, 127, 163, 235, 181, 136, 64, 137, 52, 233, 229, 171, 34, 87, 54, 204, 137, 72, 108, 190, 61, 161, 94, 29, 202, 197, 103, 71, 79, 79, 156, 240, 2, 17, 0, 0, 0, 12, 117, 227, 240, 233, 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