Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bfe00d79cb8871d18595a2a5c36278077213496d7c5f028b340f03f6d13173e

Tx prefix hash: ce3689e8903cd33f8b78c37cf6a126234f8e41189c7e724f71e81cd2b3d74575
Tx public key: 95e8344fdfc61e55feee7fc4960addb64d78d2a6ed0e63c008bb0ecd313aabe3
Timestamp: 1709333146 Timestamp [UCT]: 2024-03-01 22:45:46 Age [y:d:h:m:s]: 01:047:16:52:07
Block: 969132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295106 RingCT/type: yes/0
Extra: 0195e8344fdfc61e55feee7fc4960addb64d78d2a6ed0e63c008bb0ecd313aabe30211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4208c15ae7bcd795dcb920a69825c2233143b83f75b7cb4ceb458905c86a971 0.600000000000 1428959 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": 969142, "vin": [ { "gen": { "height": 969132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4208c15ae7bcd795dcb920a69825c2233143b83f75b7cb4ceb458905c86a971" } } ], "extra": [ 1, 149, 232, 52, 79, 223, 198, 30, 85, 254, 238, 127, 196, 150, 10, 221, 182, 77, 120, 210, 166, 237, 14, 99, 192, 8, 187, 14, 205, 49, 58, 171, 227, 2, 17, 0, 0, 0, 4, 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