Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0aeb65536391f8ba309703f3a619aded5b1372210c4dfd5ad0a61fad50e3efb3

Tx prefix hash: dca9844b950fe7def54d4c849bd6ad241e856358268e347be1a8a510b3920ee3
Tx public key: 52c8bcaa6c50c348567053bdfc6f8796022a49e4e2a75a39ec44ef5e545b2e16
Timestamp: 1736583808 Timestamp [UCT]: 2025-01-11 08:23:28 Age [y:d:h:m:s]: 00:070:01:04:18
Block: 1194907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49837 RingCT/type: yes/0
Extra: 0152c8bcaa6c50c348567053bdfc6f8796022a49e4e2a75a39ec44ef5e545b2e16021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e93eb8fcbc8523191f3b9b2deb4dc98344dc467823004303e3cb2ca80746a714 0.600000000000 1681486 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": 1194917, "vin": [ { "gen": { "height": 1194907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e93eb8fcbc8523191f3b9b2deb4dc98344dc467823004303e3cb2ca80746a714" } } ], "extra": [ 1, 82, 200, 188, 170, 108, 80, 195, 72, 86, 112, 83, 189, 252, 111, 135, 150, 2, 42, 73, 228, 226, 167, 90, 57, 236, 68, 239, 94, 84, 91, 46, 22, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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