Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cae0c3712849921084c014f00c609309e0edc0d41e7e54280fa11e09d6c09d03

Tx prefix hash: b4afd0eac6fd08131a91ee09d583c770258e1a6d3b403389dd11306b651c0247
Tx public key: a4ac94a7ae6a2d30416ea12a4251fdeb15f00bbfc488f1bf7f783f1d056d770b
Timestamp: 1761784536 Timestamp [UCT]: 2025-10-30 00:35:36 Age [y:d:h:m:s]: 00:007:21:39:58
Block: 1400858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5647 RingCT/type: yes/0
Extra: 01a4ac94a7ae6a2d30416ea12a4251fdeb15f00bbfc488f1bf7f783f1d056d770b02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc4e73b524e189084d234a145cb246c2f2b2417667e957acc1df9437a07b171b 0.600000000000 1889177 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": 1400868, "vin": [ { "gen": { "height": 1400858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc4e73b524e189084d234a145cb246c2f2b2417667e957acc1df9437a07b171b" } } ], "extra": [ 1, 164, 172, 148, 167, 174, 106, 45, 48, 65, 110, 161, 42, 66, 81, 253, 235, 21, 240, 11, 191, 196, 136, 241, 191, 127, 120, 63, 29, 5, 109, 119, 11, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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