Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 605b0991e134ec334c07321dbfb94c085a329d3ad4a468a430b5e22137e92d41

Tx prefix hash: 2005d5529ffca1eaac032141bc73223e23c0a99364eeaabedf1a8a5085723348
Tx public key: 64814ed281ec2a4b867b01e0f64c916c290bb42bacaa2e20fd0fe314bf30d9cb
Timestamp: 1700062007 Timestamp [UCT]: 2023-11-15 15:26:47 Age [y:d:h:m:s]: 01:138:11:49:08
Block: 892266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360140 RingCT/type: yes/0
Extra: 0164814ed281ec2a4b867b01e0f64c916c290bb42bacaa2e20fd0fe314bf30d9cb02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.678503886000 dcy

stealth address amount amount idx
00: 7effd202acd735fb8bd67d1ec497dcc7b6c1949c4c0975f299a62823b7083939 0.678503886000 1348367 of 0

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": 892276, "vin": [ { "gen": { "height": 892266 } } ], "vout": [ { "amount": 678503886, "target": { "key": "7effd202acd735fb8bd67d1ec497dcc7b6c1949c4c0975f299a62823b7083939" } } ], "extra": [ 1, 100, 129, 78, 210, 129, 236, 42, 75, 134, 123, 1, 224, 246, 76, 145, 108, 41, 11, 180, 43, 172, 170, 46, 32, 253, 15, 227, 20, 191, 48, 217, 203, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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