Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c888b05b69fac9e6a8381b8c92f009038ce594c50974a9e5a46b0fe0b30073df

Tx prefix hash: f8789e15c20752142d08005c9c880ca751e960dd56c73fb49631f1f39d21d4f7
Tx public key: 38c4626228ab5f73e8f89713eee468a9c80fa06a7b9e539254b1e0448af09867
Timestamp: 1729716474 Timestamp [UCT]: 2024-10-23 20:47:54 Age [y:d:h:m:s]: 00:090:18:13:31
Block: 1138084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64841 RingCT/type: yes/0
Extra: 0138c4626228ab5f73e8f89713eee468a9c80fa06a7b9e539254b1e0448af0986702110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f12d957cb43bb1cbca3de68049a7c1443de5191091a9c15f7335eeab5fa1c85 0.600000000000 1621691 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": 1138094, "vin": [ { "gen": { "height": 1138084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f12d957cb43bb1cbca3de68049a7c1443de5191091a9c15f7335eeab5fa1c85" } } ], "extra": [ 1, 56, 196, 98, 98, 40, 171, 95, 115, 232, 248, 151, 19, 238, 228, 104, 169, 200, 15, 160, 106, 123, 158, 83, 146, 84, 177, 224, 68, 138, 240, 152, 103, 2, 17, 0, 0, 0, 13, 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