Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a57b833b8f95d50ee4f27db4f95b64faa053e66d68b65736aed14edb0b729915

Tx prefix hash: 61f2c8580e9ec6fe67616307192349eefbab4cbaf7ccefca619b1fec06b30d78
Tx public key: 3cfbf709e8f2c428214bd80d53fdd49d892fd5aefe7952c3314c6fce5845c9a1
Timestamp: 1682577012 Timestamp [UCT]: 2023-04-27 06:30:12 Age [y:d:h:m:s]: 01:306:07:35:31
Block: 747551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480150 RingCT/type: yes/0
Extra: 013cfbf709e8f2c428214bd80d53fdd49d892fd5aefe7952c3314c6fce5845c9a102110000000333af99f4000000000000000000

1 output(s) for total of 2.046696376000 dcy

stealth address amount amount idx
00: 092c533e8292f113cb62cb3bae9987264783c0d09e18553d646b6523e70c395c 2.046696376000 1195238 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": 747561, "vin": [ { "gen": { "height": 747551 } } ], "vout": [ { "amount": 2046696376, "target": { "key": "092c533e8292f113cb62cb3bae9987264783c0d09e18553d646b6523e70c395c" } } ], "extra": [ 1, 60, 251, 247, 9, 232, 242, 196, 40, 33, 75, 216, 13, 83, 253, 212, 157, 137, 47, 213, 174, 254, 121, 82, 195, 49, 76, 111, 206, 88, 69, 201, 161, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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