Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 778c947b301754eca4359b9c0dc2702e9127196714e1fcd2402c73c489b15aa0

Tx prefix hash: cf5656ebd2d8ecfcf08d4b93a99bd946093e84e9a9787c2a0f6c9986d43610b8
Tx public key: 4144b0826107f0ea7e6a98952d4949c736edb018023aaf47eb0574a4854f24db
Timestamp: 1735744520 Timestamp [UCT]: 2025-01-01 15:15:20 Age [y:d:h:m:s]: 00:171:00:34:05
Block: 1187958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121894 RingCT/type: yes/0
Extra: 014144b0826107f0ea7e6a98952d4949c736edb018023aaf47eb0574a4854f24db021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dbaa1a7b9f6b0b15758b0f4265001d8ab5ba01c3af98f372c03018e60851092 0.600000000000 1674457 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": 1187968, "vin": [ { "gen": { "height": 1187958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dbaa1a7b9f6b0b15758b0f4265001d8ab5ba01c3af98f372c03018e60851092" } } ], "extra": [ 1, 65, 68, 176, 130, 97, 7, 240, 234, 126, 106, 152, 149, 45, 73, 73, 199, 54, 237, 176, 24, 2, 58, 175, 71, 235, 5, 116, 164, 133, 79, 36, 219, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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