Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3842aae7eb662cdcc4ffc6d81f185ff01ca52d5c6c471c1d348cf3f4c5fecb8a

Tx prefix hash: 677eecd8ed2580c6ab16715c3de1ecf320ade1aa4d829f14bb9fe37f51f239b7
Tx public key: 776a41b23e990d86ee8f1d6865cda7234f2439729f55246e1127f49bd68886a6
Timestamp: 1647732322 Timestamp [UCT]: 2022-03-19 23:25:22 Age [y:d:h:m:s]: 03:227:00:20:21
Block: 462132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 940132 RingCT/type: yes/0
Extra: 01776a41b23e990d86ee8f1d6865cda7234f2439729f55246e1127f49bd68886a602110000000ea8c141c5000000000000000000

1 output(s) for total of 18.061969512000 dcy

stealth address amount amount idx
00: c12fa592ceceb46f01a4cc07eab25a0b711a73455990936d575c13d7fc9f2b1b 18.061969512000 879521 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": 462142, "vin": [ { "gen": { "height": 462132 } } ], "vout": [ { "amount": 18061969512, "target": { "key": "c12fa592ceceb46f01a4cc07eab25a0b711a73455990936d575c13d7fc9f2b1b" } } ], "extra": [ 1, 119, 106, 65, 178, 62, 153, 13, 134, 238, 143, 29, 104, 101, 205, 167, 35, 79, 36, 57, 114, 159, 85, 36, 110, 17, 39, 244, 155, 214, 136, 134, 166, 2, 17, 0, 0, 0, 14, 168, 193, 65, 197, 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