Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a47c018c38188f8350cf8e2e32c790d66aba5e772e98a709d53aa1367af0bb3

Tx prefix hash: 389f2267071a10e92e1d2065a337c782aa7202a39ebfc0d36a552c84d91d6481
Tx public key: 1ca917c8a69cd744e794dcc75de3a0e570d0543e5d48fb24efc9c630b85a5036
Timestamp: 1713141363 Timestamp [UCT]: 2024-04-15 00:36:03 Age [y:d:h:m:s]: 01:038:22:41:11
Block: 1000670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288834 RingCT/type: yes/0
Extra: 011ca917c8a69cd744e794dcc75de3a0e570d0543e5d48fb24efc9c630b85a50360211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76783217b14a66f96fd6614ff5a6bad1477cb9867d8f7fb86c9e48949b408462 0.600000000000 1461168 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": 1000680, "vin": [ { "gen": { "height": 1000670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76783217b14a66f96fd6614ff5a6bad1477cb9867d8f7fb86c9e48949b408462" } } ], "extra": [ 1, 28, 169, 23, 200, 166, 156, 215, 68, 231, 148, 220, 199, 93, 227, 160, 229, 112, 208, 84, 62, 93, 72, 251, 36, 239, 201, 198, 48, 184, 90, 80, 54, 2, 17, 0, 0, 0, 3, 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