Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecadaed0242fe4c7261c6214cbf0a8ef5cf9d83781d8ec5b78f1d35768108455

Tx prefix hash: 411ce330ce173c17c93188e2e5186a0cde88032eeb937d4c850fea4c1cece2db
Tx public key: 40afb785fd1926cabf441b53f8d325f5d3c47d33d4e81715fec5df12b1146bf3
Timestamp: 1724747967 Timestamp [UCT]: 2024-08-27 08:39:27 Age [y:d:h:m:s]: 00:273:08:36:27
Block: 1096910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195270 RingCT/type: yes/0
Extra: 0140afb785fd1926cabf441b53f8d325f5d3c47d33d4e81715fec5df12b1146bf302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8581dc9c1f7322876c6b67faae8d894ffb3bf16e22ed950326ec016c7f0926c 0.600000000000 1572123 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": 1096920, "vin": [ { "gen": { "height": 1096910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8581dc9c1f7322876c6b67faae8d894ffb3bf16e22ed950326ec016c7f0926c" } } ], "extra": [ 1, 64, 175, 183, 133, 253, 25, 38, 202, 191, 68, 27, 83, 248, 211, 37, 245, 211, 196, 125, 51, 212, 232, 23, 21, 254, 197, 223, 18, 177, 20, 107, 243, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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