Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 457462b99877d58a172100ab839b5f8ab4d5c116a64816e6a164af47b635fcaa

Tx prefix hash: 405114560010796ef278f85c5bfb3f1bc6933218f4d060bf5575ff72de13949d
Tx public key: 9c3e2fd9afe3d2c8f86c97c0948f3c2fdc80c7469df04b6685eac645be23c243
Timestamp: 1735895536 Timestamp [UCT]: 2025-01-03 09:12:16 Age [y:d:h:m:s]: 00:161:21:34:00
Block: 1189230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115438 RingCT/type: yes/0
Extra: 019c3e2fd9afe3d2c8f86c97c0948f3c2fdc80c7469df04b6685eac645be23c243021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4fcac113e6cd46d6251b39f736b3dae8ea3a341d305997b53901e3c6ca0bf40 0.600000000000 1675735 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": 1189240, "vin": [ { "gen": { "height": 1189230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4fcac113e6cd46d6251b39f736b3dae8ea3a341d305997b53901e3c6ca0bf40" } } ], "extra": [ 1, 156, 62, 47, 217, 175, 227, 210, 200, 248, 108, 151, 192, 148, 143, 60, 47, 220, 128, 199, 70, 157, 240, 75, 102, 133, 234, 198, 69, 190, 35, 194, 67, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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