Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a0f3ace94defca34d5e1653d4629a4410b506df24e06875188e6c316a4c8a1d

Tx prefix hash: 58912a1201b34f1a6dcf9c4943b8a4a2cc182de397b98158c1320e63c25e3201
Tx public key: c6e5902fd77edb4f69e0ef7e19d3dfcfdd199dc43209f63c3bf7f46c1c5df7cd
Timestamp: 1711709670 Timestamp [UCT]: 2024-03-29 10:54:30 Age [y:d:h:m:s]: 01:227:09:40:07
Block: 988843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421193 RingCT/type: yes/0
Extra: 01c6e5902fd77edb4f69e0ef7e19d3dfcfdd199dc43209f63c3bf7f46c1c5df7cd02110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d45a07e10dfc02310d43804f7ad774ec8ee4230cc26fdbbf4511dd82edcac96b 0.600000000000 1449130 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": 988853, "vin": [ { "gen": { "height": 988843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d45a07e10dfc02310d43804f7ad774ec8ee4230cc26fdbbf4511dd82edcac96b" } } ], "extra": [ 1, 198, 229, 144, 47, 215, 126, 219, 79, 105, 224, 239, 126, 25, 211, 223, 207, 221, 25, 157, 196, 50, 9, 246, 60, 59, 247, 244, 108, 28, 93, 247, 205, 2, 17, 0, 0, 0, 12, 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