Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6c35fd19a7c6fc604f9f5f9134de990660d05996014daf8cc842f4b7813d126

Tx prefix hash: ba14b3f1094291502c605d05f9ba84ea9de4039aa8487c0ccf4b932c776fd2b9
Tx public key: d369ed8505dc47c4d686abcfea07b6822e456c66b2dd67c12a4d8894b331a80d
Timestamp: 1730579802 Timestamp [UCT]: 2024-11-02 20:36:42 Age [y:d:h:m:s]: 00:080:22:48:15
Block: 1145182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57872 RingCT/type: yes/0
Extra: 01d369ed8505dc47c4d686abcfea07b6822e456c66b2dd67c12a4d8894b331a80d0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ce9498b8f0105263571286591754e4d2113545b261d58f4c2b4b60ad4f97354 0.600000000000 1629579 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": 1145192, "vin": [ { "gen": { "height": 1145182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ce9498b8f0105263571286591754e4d2113545b261d58f4c2b4b60ad4f97354" } } ], "extra": [ 1, 211, 105, 237, 133, 5, 220, 71, 196, 214, 134, 171, 207, 234, 7, 182, 130, 46, 69, 108, 102, 178, 221, 103, 193, 42, 77, 136, 148, 179, 49, 168, 13, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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