Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aab638ec3ee481764545e8a2eed4ac4b853ad5c1dadd20b5d05ef0c843b6470f

Tx prefix hash: ccedbec7f95a372cd97d6f018a4c715a4c2ea667f82f3fe6522710540354d8f4
Tx public key: 78e30adc739a43dcfe0a4b79a77e9779e6efbe1eff645a887b31f8cd852e8f6e
Timestamp: 1718723440 Timestamp [UCT]: 2024-06-18 15:10:40 Age [y:d:h:m:s]: 00:293:11:31:49
Block: 1046972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209710 RingCT/type: yes/0
Extra: 0178e30adc739a43dcfe0a4b79a77e9779e6efbe1eff645a887b31f8cd852e8f6e02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dca4659426980e23dbd790aa11c00276c67aac97f67e6973f5fa6c5a68a30810 0.600000000000 1516791 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": 1046982, "vin": [ { "gen": { "height": 1046972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dca4659426980e23dbd790aa11c00276c67aac97f67e6973f5fa6c5a68a30810" } } ], "extra": [ 1, 120, 227, 10, 220, 115, 154, 67, 220, 254, 10, 75, 121, 167, 126, 151, 121, 230, 239, 190, 30, 255, 100, 90, 136, 123, 49, 248, 205, 133, 46, 143, 110, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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