Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c951bb02d877f8d0a894921dbeb1cbc6c9547d6a6774789a90a75e34485b0f68

Tx prefix hash: 4399e12873d298802ce99668c81f64e9aee34c4ff614f0e319740c51abc4a2bc
Tx public key: b1783c7c8b22301c4760cefa8688c01db7eaa7a6ee77116b846337ff1101ede6
Timestamp: 1725771818 Timestamp [UCT]: 2024-09-08 05:03:38 Age [y:d:h:m:s]: 00:209:05:57:57
Block: 1105410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149384 RingCT/type: yes/0
Extra: 01b1783c7c8b22301c4760cefa8688c01db7eaa7a6ee77116b846337ff1101ede6021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75d2acbf7ff502db0401b429fa4d9bcd9dd9622d22f3d2c0dc893f9df3708ca7 0.600000000000 1582753 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": 1105420, "vin": [ { "gen": { "height": 1105410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75d2acbf7ff502db0401b429fa4d9bcd9dd9622d22f3d2c0dc893f9df3708ca7" } } ], "extra": [ 1, 177, 120, 60, 124, 139, 34, 48, 28, 71, 96, 206, 250, 134, 136, 192, 29, 183, 234, 167, 166, 238, 119, 17, 107, 132, 99, 55, 255, 17, 1, 237, 230, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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