Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 286d85552fcec1fae4cb89e4a564a5ee0ffa9b5cbe98af183dd273389e5264fd

Tx prefix hash: 50e32ad0bd093888ad7e6ac55b6db9ecbb6b34ae733cb4f0c2c5d248f593945e
Tx public key: b3e713bdf62b827092798dd5c806c9882972cd3a765720cf917c67d42d63a6b1
Timestamp: 1747772791 Timestamp [UCT]: 2025-05-20 20:26:31 Age [y:d:h:m:s]: 00:216:23:48:45
Block: 1287277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152819 RingCT/type: yes/0
Extra: 01b3e713bdf62b827092798dd5c806c9882972cd3a765720cf917c67d42d63a6b10211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90412127b6f2898bd7da922b97fb6cbcf39398815cc5eec8d53db7a9c237011d 0.600000000000 1774744 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": 1287287, "vin": [ { "gen": { "height": 1287277 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90412127b6f2898bd7da922b97fb6cbcf39398815cc5eec8d53db7a9c237011d" } } ], "extra": [ 1, 179, 231, 19, 189, 246, 43, 130, 112, 146, 121, 141, 213, 200, 6, 201, 136, 41, 114, 205, 58, 118, 87, 32, 207, 145, 124, 103, 212, 45, 99, 166, 177, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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