Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04c9606fa482c82cdb7565eccdcf9895de9dfe054b9d8b90230452f7d65aa167

Tx prefix hash: baed2cecc5bf4828959cc33457805300f6abfd270f63b2aad0656607d296071e
Tx public key: 4c4917eaaf537af91031494d9979393e5640d70fa36c70e07c0d691c3fd41c2b
Timestamp: 1723147375 Timestamp [UCT]: 2024-08-08 20:02:55 Age [y:d:h:m:s]: 00:251:00:35:21
Block: 1083645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179306 RingCT/type: yes/0
Extra: 014c4917eaaf537af91031494d9979393e5640d70fa36c70e07c0d691c3fd41c2b021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0190cefcfb4d1b18dfa5f3d85e5a7368c6b52c74412c84d7e93e957c0c6f3c95 0.600000000000 1557640 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": 1083655, "vin": [ { "gen": { "height": 1083645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0190cefcfb4d1b18dfa5f3d85e5a7368c6b52c74412c84d7e93e957c0c6f3c95" } } ], "extra": [ 1, 76, 73, 23, 234, 175, 83, 122, 249, 16, 49, 73, 77, 153, 121, 57, 62, 86, 64, 215, 15, 163, 108, 112, 224, 124, 13, 105, 28, 63, 212, 28, 43, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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