Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d10d4ee713edb7c7960c04e5386b7aef68358267abadd223b9117ed84cedd41

Tx prefix hash: 55845e158e323776c8dbc8c7cb074f136f76c9964114db136e8e5c5fc7588ddb
Tx public key: 1eb1959a036e2318d89cb22628d7df6118456000fc347008fc2b5a6a0b1486a0
Timestamp: 1732409299 Timestamp [UCT]: 2024-11-24 00:48:19 Age [y:d:h:m:s]: 00:153:21:57:22
Block: 1160334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109839 RingCT/type: yes/0
Extra: 011eb1959a036e2318d89cb22628d7df6118456000fc347008fc2b5a6a0b1486a00211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b2cc7c978b6e16caf52a7b3794a2ba8cc858b7679212a6c56049124d2e82c5c 0.600000000000 1645979 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": 1160344, "vin": [ { "gen": { "height": 1160334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b2cc7c978b6e16caf52a7b3794a2ba8cc858b7679212a6c56049124d2e82c5c" } } ], "extra": [ 1, 30, 177, 149, 154, 3, 110, 35, 24, 216, 156, 178, 38, 40, 215, 223, 97, 24, 69, 96, 0, 252, 52, 112, 8, 252, 43, 90, 106, 11, 20, 134, 160, 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