Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4d174ecf9041c3f7924b4eacb453f1ff0e450b324e2f12d5e8e542c90de2581

Tx prefix hash: fb225f5495bf9a0af927cebf08d4f99c9d504be507151366d1aaa1416efd4347
Tx public key: 7ff2196834b129862cdfe2b1b4a5ac424ec8d9456c445af9b85705d51df1c7b2
Timestamp: 1675024399 Timestamp [UCT]: 2023-01-29 20:33:19 Age [y:d:h:m:s]: 02:073:20:02:49
Block: 685577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 574391 RingCT/type: yes/0
Extra: 017ff2196834b129862cdfe2b1b4a5ac424ec8d9456c445af9b85705d51df1c7b2021100000001835e4d22000000000000000000

1 output(s) for total of 3.283966641000 dcy

stealth address amount amount idx
00: d88b143c1813c145cad20e1eaa97c58805643ffd8f56ebe52616d006ca21c3c7 3.283966641000 1127926 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": 685587, "vin": [ { "gen": { "height": 685577 } } ], "vout": [ { "amount": 3283966641, "target": { "key": "d88b143c1813c145cad20e1eaa97c58805643ffd8f56ebe52616d006ca21c3c7" } } ], "extra": [ 1, 127, 242, 25, 104, 52, 177, 41, 134, 44, 223, 226, 177, 180, 165, 172, 66, 78, 200, 217, 69, 108, 68, 90, 249, 184, 87, 5, 213, 29, 241, 199, 178, 2, 17, 0, 0, 0, 1, 131, 94, 77, 34, 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