Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de7a8964c3fd617c3c570dc1e9ea78ddfe25a1345a91d21bbf547159ffb9b5e8

Tx prefix hash: b12c2dc2ca4c729437f31f56332565e45dedfd21f472f40e30240646a5adb334
Tx public key: 9c1dfe43a4c2a5d2f7a193d48427522fe951c532e773b773d51e27d7d67617cb
Timestamp: 1736884539 Timestamp [UCT]: 2025-01-14 19:55:39 Age [y:d:h:m:s]: 00:155:11:58:09
Block: 1197396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110816 RingCT/type: yes/0
Extra: 019c1dfe43a4c2a5d2f7a193d48427522fe951c532e773b773d51e27d7d67617cb021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 289b8a0c295ed3ae0ef7eb86e3b6f966418c5833f93485d181fc989d78d0fd59 0.600000000000 1684003 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": 1197406, "vin": [ { "gen": { "height": 1197396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "289b8a0c295ed3ae0ef7eb86e3b6f966418c5833f93485d181fc989d78d0fd59" } } ], "extra": [ 1, 156, 29, 254, 67, 164, 194, 165, 210, 247, 161, 147, 212, 132, 39, 82, 47, 233, 81, 197, 50, 231, 115, 183, 115, 213, 30, 39, 215, 214, 118, 23, 203, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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