Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38109e4c98cd0c0495bbeee64fef77326c2fac37dc8a47601dca9728f0f7188f

Tx prefix hash: 80b78d1cf07fd5fde53b09778ca90e29d2c3a4a26a8b00acfd353c6c5c368bf8
Tx public key: 4e727505be11c4bfeae6f78cf7a57c3f0a0c5baa0721dc12c52118b44eea6530
Timestamp: 1574377176 Timestamp [UCT]: 2019-11-21 22:59:36 Age [y:d:h:m:s]: 05:345:12:48:32
Block: 13996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1387913 RingCT/type: yes/0
Extra: 014e727505be11c4bfeae6f78cf7a57c3f0a0c5baa0721dc12c52118b44eea6530021100000002ccefb800000000000000000000

1 output(s) for total of 551.602629261000 dcy

stealth address amount amount idx
00: 20de62e66613d69bb6d8893a719b3861f22d9d823a92819995ee9b8eaf2ed1e7 551.602629261000 17213 of 0

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": 14006, "vin": [ { "gen": { "height": 13996 } } ], "vout": [ { "amount": 551602629261, "target": { "key": "20de62e66613d69bb6d8893a719b3861f22d9d823a92819995ee9b8eaf2ed1e7" } } ], "extra": [ 1, 78, 114, 117, 5, 190, 17, 196, 191, 234, 230, 247, 140, 247, 165, 124, 63, 10, 12, 91, 170, 7, 33, 220, 18, 197, 33, 24, 180, 78, 234, 101, 48, 2, 17, 0, 0, 0, 2, 204, 239, 184, 0, 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