Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9aade8dddb02246972a6dfb6c13e423cdb78a9c8370b5364bf33d978bba901ea

Tx prefix hash: 36349adff2af659e02264472906dfd7f677fe9286b9310b8befd82ab535720fd
Tx public key: 3a5ca38577365fca97d53c08e4e07f0a781b17408e51f4b0e82ab24e9a62a39d
Timestamp: 1686340449 Timestamp [UCT]: 2023-06-09 19:54:09 Age [y:d:h:m:s]: 01:303:10:37:39
Block: 778756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478038 RingCT/type: yes/0
Extra: 013a5ca38577365fca97d53c08e4e07f0a781b17408e51f4b0e82ab24e9a62a39d021100000001faf35c9c000000000000000000

1 output(s) for total of 1.613088726000 dcy

stealth address amount amount idx
00: 72f4b0f99ae1f3617b69594d15883ef132b808fc143e990701d4ede4d49059a4 1.613088726000 1228395 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": 778766, "vin": [ { "gen": { "height": 778756 } } ], "vout": [ { "amount": 1613088726, "target": { "key": "72f4b0f99ae1f3617b69594d15883ef132b808fc143e990701d4ede4d49059a4" } } ], "extra": [ 1, 58, 92, 163, 133, 119, 54, 95, 202, 151, 213, 60, 8, 228, 224, 127, 10, 120, 27, 23, 64, 142, 81, 244, 176, 232, 42, 178, 78, 154, 98, 163, 157, 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