Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c2e851379e727d4b1f5ef732e6605a74168a3ffbdae01785ae9c6310e018008

Tx prefix hash: 4eb8177a46fe2ed40ccc7abe7f0b6f14efc73b8e545236b39a5602ee465cde8c
Tx public key: e825fb5dad217fa8b2baa42f8c64ffde8d037306e1349b49f13317ede6edc249
Timestamp: 1735725402 Timestamp [UCT]: 2025-01-01 09:56:42 Age [y:d:h:m:s]: 00:097:10:16:20
Block: 1187790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69416 RingCT/type: yes/0
Extra: 01e825fb5dad217fa8b2baa42f8c64ffde8d037306e1349b49f13317ede6edc249021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f601bc044bf84756e0ffc4b5879a3f77ab07a1e2c278bddcf786f1ecd11a1520 0.600000000000 1674287 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": 1187800, "vin": [ { "gen": { "height": 1187790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f601bc044bf84756e0ffc4b5879a3f77ab07a1e2c278bddcf786f1ecd11a1520" } } ], "extra": [ 1, 232, 37, 251, 93, 173, 33, 127, 168, 178, 186, 164, 47, 140, 100, 255, 222, 141, 3, 115, 6, 225, 52, 155, 73, 241, 51, 23, 237, 230, 237, 194, 73, 2, 17, 0, 0, 0, 3, 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