Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04c5d69fd97fc333ba936639c9d2510987187e0ca9db01b15ce16fa6f7d2374d

Tx prefix hash: acf6ef2b844db452029b9d749fb543d600eefffc2402923f162d338e6acb3dc4
Tx public key: 1eda8eb8e0df30000eca86b6390c873d7f76b4a2bbc3337d05fadc42f97be184
Timestamp: 1722424575 Timestamp [UCT]: 2024-07-31 11:16:15 Age [y:d:h:m:s]: 00:301:14:05:28
Block: 1077652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215496 RingCT/type: yes/0
Extra: 011eda8eb8e0df30000eca86b6390c873d7f76b4a2bbc3337d05fadc42f97be184021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 681766f64261310c0d42cd2f3574dfccd5a974436749d1cae7aa56cbe3d3a406 0.600000000000 1550207 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": 1077662, "vin": [ { "gen": { "height": 1077652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "681766f64261310c0d42cd2f3574dfccd5a974436749d1cae7aa56cbe3d3a406" } } ], "extra": [ 1, 30, 218, 142, 184, 224, 223, 48, 0, 14, 202, 134, 182, 57, 12, 135, 61, 127, 118, 180, 162, 187, 195, 51, 125, 5, 250, 220, 66, 249, 123, 225, 132, 2, 17, 0, 0, 0, 4, 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