Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e28c62e86308dac5acebe01b8d4bdb247b6fb112915f105e5b1214d53e4b243

Tx prefix hash: 04b4118d6c44142e97ad7ca3a946e2c3c4a841023dea57ea0565f664d6d60a34
Tx public key: 14c1a72c3ae8e5b1bd496485459f944994b717d143e8c63b9eb63bf2ac61265e
Timestamp: 1720532665 Timestamp [UCT]: 2024-07-09 13:44:25 Age [y:d:h:m:s]: 01:127:06:19:52
Block: 1061975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349475 RingCT/type: yes/0
Extra: 0114c1a72c3ae8e5b1bd496485459f944994b717d143e8c63b9eb63bf2ac61265e02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f90deb780e37449023ffff27dbf2ef0ecd6a8d762a2a70d89d17b27f6e304487 0.600000000000 1532474 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": 1061985, "vin": [ { "gen": { "height": 1061975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f90deb780e37449023ffff27dbf2ef0ecd6a8d762a2a70d89d17b27f6e304487" } } ], "extra": [ 1, 20, 193, 167, 44, 58, 232, 229, 177, 189, 73, 100, 133, 69, 159, 148, 73, 148, 183, 23, 209, 67, 232, 198, 59, 158, 182, 59, 242, 172, 97, 38, 94, 2, 17, 0, 0, 0, 7, 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