Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 749f40ce2fc330666d7ca974c4889d1b49cfaa172c8be786e56537a6d45854e6

Tx prefix hash: 3f14754d3cc57aa0562dce9335f7fb0b6a0efa72fc85f0e14803670b7855a1f3
Tx public key: c671cf31443250d9bef6cf61b5a472860dab7a8d320899a414c5b1675e8a436a
Timestamp: 1675151048 Timestamp [UCT]: 2023-01-31 07:44:08 Age [y:d:h:m:s]: 02:117:09:08:00
Block: 686604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 605569 RingCT/type: yes/0
Extra: 01c671cf31443250d9bef6cf61b5a472860dab7a8d320899a414c5b1675e8a436a0211000000035029cbac000000000000000000

1 output(s) for total of 3.258335934000 dcy

stealth address amount amount idx
00: 897dc7151fbef4dec80f2c023d7114adcbc21e355030d9c813b1192bc9a413c5 3.258335934000 1129109 of 0

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": 686614, "vin": [ { "gen": { "height": 686604 } } ], "vout": [ { "amount": 3258335934, "target": { "key": "897dc7151fbef4dec80f2c023d7114adcbc21e355030d9c813b1192bc9a413c5" } } ], "extra": [ 1, 198, 113, 207, 49, 68, 50, 80, 217, 190, 246, 207, 97, 181, 164, 114, 134, 13, 171, 122, 141, 50, 8, 153, 164, 20, 197, 177, 103, 94, 138, 67, 106, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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