Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 540496272f43027ab156257a4737ca8ffb8e55085ec138316d6b04d519c7d8e8

Tx prefix hash: 8e8df7dcf58069bdfc0260145ab26b250e4279859f21844e4e7266fec18a4fb5
Tx public key: ee76e55dec85b5b3bf3216402fa7d730977e1f9b712ce6122ee9e42f3bdd0898
Timestamp: 1725271597 Timestamp [UCT]: 2024-09-02 10:06:37 Age [y:d:h:m:s]: 00:083:08:49:06
Block: 1101258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59617 RingCT/type: yes/0
Extra: 01ee76e55dec85b5b3bf3216402fa7d730977e1f9b712ce6122ee9e42f3bdd089802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53baf4a075be73b993c2f1c81ba917189aed4fb8fca5020e62e73dcd7ea7f1a6 0.600000000000 1577245 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": 1101268, "vin": [ { "gen": { "height": 1101258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53baf4a075be73b993c2f1c81ba917189aed4fb8fca5020e62e73dcd7ea7f1a6" } } ], "extra": [ 1, 238, 118, 229, 93, 236, 133, 181, 179, 191, 50, 22, 64, 47, 167, 215, 48, 151, 126, 31, 155, 113, 44, 230, 18, 46, 233, 228, 47, 59, 221, 8, 152, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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