Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 008c3813f4c6720c0e373fa164dfbd1bdb9b22a28cfc5aa5f091e02c37164b09

Tx prefix hash: 812b91d71146aa58018e565743cc638c1345c9fc2845a97c75007f4b935db633
Tx public key: 3b0ff14fcddf7e82e409471e6362011cf23ac3a0d9bc831af2c3c4ea3af66f46
Timestamp: 1706713630 Timestamp [UCT]: 2024-01-31 15:07:10 Age [y:d:h:m:s]: 01:063:19:15:07
Block: 947384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306682 RingCT/type: yes/0
Extra: 013b0ff14fcddf7e82e409471e6362011cf23ac3a0d9bc831af2c3c4ea3af66f4602110000000381d71d55000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86d3211ce7ec42e6a56000adb0dbd032e2073b8d396a315d8040768f7c9de375 0.600000000000 1405732 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": 947394, "vin": [ { "gen": { "height": 947384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86d3211ce7ec42e6a56000adb0dbd032e2073b8d396a315d8040768f7c9de375" } } ], "extra": [ 1, 59, 15, 241, 79, 205, 223, 126, 130, 228, 9, 71, 30, 99, 98, 1, 28, 242, 58, 195, 160, 217, 188, 131, 26, 242, 195, 196, 234, 58, 246, 111, 70, 2, 17, 0, 0, 0, 3, 129, 215, 29, 85, 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