Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea2e962bf8b05bc6eff636401e787d24571f8928f5bdc0175ba1d93c430a0e7b

Tx prefix hash: 813055d872f9bbbbc57a1dc984624ce912431cd30b00c1c57109959c39d8e312
Tx public key: c77cf545e848eb6942381be5d1c2d845687bf961466ae01918414a4a57b18de4
Timestamp: 1698727315 Timestamp [UCT]: 2023-10-31 04:41:55 Age [y:d:h:m:s]: 01:082:03:39:38
Block: 881400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319886 RingCT/type: yes/0
Extra: 01c77cf545e848eb6942381be5d1c2d845687bf961466ae01918414a4a57b18de402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.737150092000 dcy

stealth address amount amount idx
00: b09f68aa1c33cd960947a66232353b9cd87f7212845cdd0ff7aa91206f3d3364 0.737150092000 1336982 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": 881410, "vin": [ { "gen": { "height": 881400 } } ], "vout": [ { "amount": 737150092, "target": { "key": "b09f68aa1c33cd960947a66232353b9cd87f7212845cdd0ff7aa91206f3d3364" } } ], "extra": [ 1, 199, 124, 245, 69, 232, 72, 235, 105, 66, 56, 27, 229, 209, 194, 216, 69, 104, 123, 249, 97, 70, 106, 224, 25, 24, 65, 74, 74, 87, 177, 141, 228, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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