Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fae0e4e04301f8f747175112c63fb2f2aed6d119654ad7723cc00a6805d41cb

Tx prefix hash: 0c24791f43f78b8cc8f8d83e705d458179411163f1b13518521d4701a2dc0737
Tx public key: 811851a935fe57351a4e202d98b6b456487f1e3ed6bc533d803c644327693354
Timestamp: 1699088401 Timestamp [UCT]: 2023-11-04 09:00:01 Age [y:d:h:m:s]: 01:154:16:51:38
Block: 884394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371544 RingCT/type: yes/0
Extra: 01811851a935fe57351a4e202d98b6b456487f1e3ed6bc533d803c644327693354021100000003faf35c9c000000000000000000

1 output(s) for total of 0.720502604000 dcy

stealth address amount amount idx
00: 96b12e1b77bdd98d7d7e677314d9be9948a7ed3e651d51950f32dfc61681d0a1 0.720502604000 1340133 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": 884404, "vin": [ { "gen": { "height": 884394 } } ], "vout": [ { "amount": 720502604, "target": { "key": "96b12e1b77bdd98d7d7e677314d9be9948a7ed3e651d51950f32dfc61681d0a1" } } ], "extra": [ 1, 129, 24, 81, 169, 53, 254, 87, 53, 26, 78, 32, 45, 152, 182, 180, 86, 72, 127, 30, 62, 214, 188, 83, 61, 128, 60, 100, 67, 39, 105, 51, 84, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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