Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b31b80e310d2f8789f7d2d80b2cfa0ad344eb64fe51f6a3904ba78f5ed8a4a44

Tx prefix hash: 129672fd6b277c2ef0ca37d0055a5583cea948bf3291703b39476f7b393792be
Tx public key: aa2da53e8516136f8e71d16b72f2b203fdcce2b6b9f0b297c3998c3852b1b489
Timestamp: 1705096857 Timestamp [UCT]: 2024-01-12 22:00:57 Age [y:d:h:m:s]: 01:324:15:09:12
Block: 933984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490868 RingCT/type: yes/0
Extra: 01aa2da53e8516136f8e71d16b72f2b203fdcce2b6b9f0b297c3998c3852b1b4890211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6efd7b3779f756eb2dc4358a9345d888dd49479f3b8eb0fe95d9a6b39dec19a1 0.600000000000 1391968 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": 933994, "vin": [ { "gen": { "height": 933984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6efd7b3779f756eb2dc4358a9345d888dd49479f3b8eb0fe95d9a6b39dec19a1" } } ], "extra": [ 1, 170, 45, 165, 62, 133, 22, 19, 111, 142, 113, 209, 107, 114, 242, 178, 3, 253, 204, 226, 182, 185, 240, 178, 151, 195, 153, 140, 56, 82, 177, 180, 137, 2, 17, 0, 0, 0, 9, 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