Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c779dbe33f124c31cab5b6d2218a2193bacc6dbadd086aa5b31a010757bcf3b2

Tx prefix hash: de2b5772632055af74e05f5c8667a73968f7ea1b91f443b85fc5f2d306b1e7da
Tx public key: 4f02e8cb1c6063cad985b182d1ec8b05590171cf790784ee7365db31c8f80bf3
Timestamp: 1738160208 Timestamp [UCT]: 2025-01-29 14:16:48 Age [y:d:h:m:s]: 00:296:03:33:48
Block: 1207693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209412 RingCT/type: yes/0
Extra: 014f02e8cb1c6063cad985b182d1ec8b05590171cf790784ee7365db31c8f80bf302110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af7a93a2a3ab757bf7a611bd6166b88eb465d7a66ae19f173e3f8df6fde9eccb 0.600000000000 1694418 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": 1207703, "vin": [ { "gen": { "height": 1207693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af7a93a2a3ab757bf7a611bd6166b88eb465d7a66ae19f173e3f8df6fde9eccb" } } ], "extra": [ 1, 79, 2, 232, 203, 28, 96, 99, 202, 217, 133, 177, 130, 209, 236, 139, 5, 89, 1, 113, 207, 121, 7, 132, 238, 115, 101, 219, 49, 200, 248, 11, 243, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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