Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79430274ebe2c4c208b2f20b94df99071b9b76c1cff5d52e9350d7550478cbd1

Tx prefix hash: bf37435f23f77fba547c482222dc9e31af13f0fbab537a1df17234068559306a
Tx public key: 69d8d1358f543f06d5e6f101ee9bc080cbc19620e3ce971d306fc21ad3060531
Timestamp: 1725995955 Timestamp [UCT]: 2024-09-10 19:19:15 Age [y:d:h:m:s]: 00:120:10:29:22
Block: 1107261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86138 RingCT/type: yes/0
Extra: 0169d8d1358f543f06d5e6f101ee9bc080cbc19620e3ce971d306fc21ad306053102110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8664b5da59a1cf03a3c76c52f89b1e3fdff8044e4c09b58ab0c8a2f2a48a79f 0.600000000000 1584872 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": 1107271, "vin": [ { "gen": { "height": 1107261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8664b5da59a1cf03a3c76c52f89b1e3fdff8044e4c09b58ab0c8a2f2a48a79f" } } ], "extra": [ 1, 105, 216, 209, 53, 143, 84, 63, 6, 213, 230, 241, 1, 238, 155, 192, 128, 203, 193, 150, 32, 227, 206, 151, 29, 48, 111, 194, 26, 211, 6, 5, 49, 2, 17, 0, 0, 0, 6, 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