Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98fec78bf7f1098df57b14b319b2db9f2f447db46221f7fd873f6a70b913e414

Tx prefix hash: 437874350ad78248c30e4dcd0faee2d44a4a39ab33969ea1638a5dee1be886f4
Tx public key: ece7a47a7287a23f4cc7057c30753937cdb64be99ba8f17f11d581c2558e874b
Timestamp: 1723295901 Timestamp [UCT]: 2024-08-10 13:18:21 Age [y:d:h:m:s]: 00:234:07:09:56
Block: 1084883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167324 RingCT/type: yes/0
Extra: 01ece7a47a7287a23f4cc7057c30753937cdb64be99ba8f17f11d581c2558e874b021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d379a38c414e5af88d0593783582f7633883929e21a32bddc324644b0e967c4 0.600000000000 1559318 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": 1084893, "vin": [ { "gen": { "height": 1084883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d379a38c414e5af88d0593783582f7633883929e21a32bddc324644b0e967c4" } } ], "extra": [ 1, 236, 231, 164, 122, 114, 135, 162, 63, 76, 199, 5, 124, 48, 117, 57, 55, 205, 182, 75, 233, 155, 168, 241, 127, 17, 213, 129, 194, 85, 142, 135, 75, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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