Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa3c6308790d175f2e144f463708e164a06ec2ef6c9d8f9577d1f7c1cdcdcb74

Tx prefix hash: 0a8ebeeb9ac9e5c8b6fe1aea4557ef08192831553f34597e47eec658dfe420e4
Tx public key: f6ced4eaee1f180a5382e153b03f92b6de140624f73b5b8001924f02c84fb0e8
Timestamp: 1741197554 Timestamp [UCT]: 2025-03-05 17:59:14 Age [y:d:h:m:s]: 00:265:21:13:06
Block: 1232834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187783 RingCT/type: yes/0
Extra: 01f6ced4eaee1f180a5382e153b03f92b6de140624f73b5b8001924f02c84fb0e80211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 223d7f08332e05b80575185f3bbb2cc782aa6c7dd2783f7551c1f6dbbe5afbf0 0.600000000000 1719749 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": 1232844, "vin": [ { "gen": { "height": 1232834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "223d7f08332e05b80575185f3bbb2cc782aa6c7dd2783f7551c1f6dbbe5afbf0" } } ], "extra": [ 1, 246, 206, 212, 234, 238, 31, 24, 10, 83, 130, 225, 83, 176, 63, 146, 182, 222, 20, 6, 36, 247, 59, 91, 128, 1, 146, 79, 2, 200, 79, 176, 232, 2, 17, 0, 0, 0, 2, 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