Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 009ae626383f4c4a964c969b789ec3b1a577bba7a585a6c3f20c6f3441739ff7

Tx prefix hash: b74cd8eeda621c749d8ddee4689f5c3a68c5ff13f828dac5187ae236518e0d56
Tx public key: 55d44076052f668f285942e8cf0a5e09cce0e01e38f2e3e6fe8a2c00d6ea1bc9
Timestamp: 1732265300 Timestamp [UCT]: 2024-11-22 08:48:20 Age [y:d:h:m:s]: 00:001:22:04:38
Block: 1159145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1372 RingCT/type: yes/0
Extra: 0155d44076052f668f285942e8cf0a5e09cce0e01e38f2e3e6fe8a2c00d6ea1bc902110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bd85eb27c6c88b518cb7e03a28ea6a29c79cfa4fe530db0c324a58cc900f28a 0.600000000000 1644776 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": 1159155, "vin": [ { "gen": { "height": 1159145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bd85eb27c6c88b518cb7e03a28ea6a29c79cfa4fe530db0c324a58cc900f28a" } } ], "extra": [ 1, 85, 212, 64, 118, 5, 47, 102, 143, 40, 89, 66, 232, 207, 10, 94, 9, 204, 224, 224, 30, 56, 242, 227, 230, 254, 138, 44, 0, 214, 234, 27, 201, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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