Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ab7bafcc9d59917c6ec25bd37074edac9631ab72fee9fc5cc3555981654e276

Tx prefix hash: 5521621ca621c12ec52b705aee5d5e295cfa69291bd888bdc55a92efeb76ca7b
Tx public key: 91bada6b8eee080c1846bfe2655bd6bf124c896af55d57b8d9a67b25d6aa4c66
Timestamp: 1704174346 Timestamp [UCT]: 2024-01-02 05:45:46 Age [y:d:h:m:s]: 01:114:08:46:22
Block: 926345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342866 RingCT/type: yes/0
Extra: 0191bada6b8eee080c1846bfe2655bd6bf124c896af55d57b8d9a67b25d6aa4c660211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c9953366d347cbfd1f7f4aebd0b92059952912e64eaebe85e15e8a6457b2bab 0.600000000000 1384127 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": 926355, "vin": [ { "gen": { "height": 926345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c9953366d347cbfd1f7f4aebd0b92059952912e64eaebe85e15e8a6457b2bab" } } ], "extra": [ 1, 145, 186, 218, 107, 142, 238, 8, 12, 24, 70, 191, 226, 101, 91, 214, 191, 18, 76, 137, 106, 245, 93, 87, 184, 217, 166, 123, 37, 214, 170, 76, 102, 2, 17, 0, 0, 0, 1, 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