Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4312ebfdd91e5a3e975737be180d3826ae1010cd38037f55ed79c25b8516fe71

Tx prefix hash: afbd5ef2a421286e981a42b14ee7aa21c5643db84ab764213e1ae0e909b14e7f
Tx public key: 549427ace76eaa8d64dfb8248a0cde17a68192a38e61da0cbbead6a20239e753
Timestamp: 1710615557 Timestamp [UCT]: 2024-03-16 18:59:17 Age [y:d:h:m:s]: 01:238:02:58:11
Block: 979768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428883 RingCT/type: yes/0
Extra: 01549427ace76eaa8d64dfb8248a0cde17a68192a38e61da0cbbead6a20239e7530211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9df8d27e1c4cd04ae465a178ee8d4424b889362ff9638b19ad14da328f8be34e 0.600000000000 1439821 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": 979778, "vin": [ { "gen": { "height": 979768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9df8d27e1c4cd04ae465a178ee8d4424b889362ff9638b19ad14da328f8be34e" } } ], "extra": [ 1, 84, 148, 39, 172, 231, 110, 170, 141, 100, 223, 184, 36, 138, 12, 222, 23, 166, 129, 146, 163, 142, 97, 218, 12, 187, 234, 214, 162, 2, 57, 231, 83, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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