Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 833fb7a4b5237497936ee22007016c384586ff70824bb888424a2ce66409dd03

Tx prefix hash: 0eb15efb9aeefdc6089cb6bcfd0eedf2c0d91c2a2ab7dbc6a2e3d452b609c8c0
Tx public key: f4c7f1248dab4e250c5923faf8cd6812a6bb83cc8fa6505b15151323d78b33ec
Timestamp: 1681199223 Timestamp [UCT]: 2023-04-11 07:47:03 Age [y:d:h:m:s]: 01:362:21:09:01
Block: 736119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520628 RingCT/type: yes/0
Extra: 01f4c7f1248dab4e250c5923faf8cd6812a6bb83cc8fa6505b15151323d78b33ec021100000001b3164c24000000000000000000

1 output(s) for total of 2.233224578000 dcy

stealth address amount amount idx
00: 7a0b7639d24ae710016475d17e328ac563228eb6d1f97a8e945b9b1ed2e73378 2.233224578000 1182518 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": 736129, "vin": [ { "gen": { "height": 736119 } } ], "vout": [ { "amount": 2233224578, "target": { "key": "7a0b7639d24ae710016475d17e328ac563228eb6d1f97a8e945b9b1ed2e73378" } } ], "extra": [ 1, 244, 199, 241, 36, 141, 171, 78, 37, 12, 89, 35, 250, 248, 205, 104, 18, 166, 187, 131, 204, 143, 166, 80, 91, 21, 21, 19, 35, 215, 139, 51, 236, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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