Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f549d3d3d04a510bd28289654e85f643889b44a2757115323b1f241cdea93977

Tx prefix hash: a4d7d72e81a65955d883f39dbee1bee4bb3ad67fc823badca00ac19e757fb0fb
Tx public key: 255e6aef958b463f5babeb21b5ff9d1030d8e9cf183abd1489c56f1eb8faa915
Timestamp: 1715516307 Timestamp [UCT]: 2024-05-12 12:18:27 Age [y:d:h:m:s]: 00:332:10:02:02
Block: 1020416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237571 RingCT/type: yes/0
Extra: 01255e6aef958b463f5babeb21b5ff9d1030d8e9cf183abd1489c56f1eb8faa91502110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 543042bf5fce7af3309d0f5e7543cb750e395524d227d2afffe45c1b17248de5 0.600000000000 1484487 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": 1020426, "vin": [ { "gen": { "height": 1020416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "543042bf5fce7af3309d0f5e7543cb750e395524d227d2afffe45c1b17248de5" } } ], "extra": [ 1, 37, 94, 106, 239, 149, 139, 70, 63, 91, 171, 235, 33, 181, 255, 157, 16, 48, 216, 233, 207, 24, 58, 189, 20, 137, 197, 111, 30, 184, 250, 169, 21, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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