Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32ffd10b13c3b3a4cf17bba0fed9cbe12e2adb27f8170db8b0f898aabc40bbf5

Tx prefix hash: e3201749819fbd37ba0d5a0af90f7f89c5dbb0d9045fcadfd6550c217760e7ee
Tx public key: 67baeae88dd48ac7641e109883ff0a04b413e817dadd4eda66a4bca73e7503b2
Timestamp: 1707212971 Timestamp [UCT]: 2024-02-06 09:49:31 Age [y:d:h:m:s]: 01:075:22:53:09
Block: 951534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315348 RingCT/type: yes/0
Extra: 0167baeae88dd48ac7641e109883ff0a04b413e817dadd4eda66a4bca73e7503b20211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a07ed4f572a229de84c8dc06e2d94581da83bda3843c3bd99fc50e2cd407c71 0.600000000000 1410312 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": 951544, "vin": [ { "gen": { "height": 951534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a07ed4f572a229de84c8dc06e2d94581da83bda3843c3bd99fc50e2cd407c71" } } ], "extra": [ 1, 103, 186, 234, 232, 141, 212, 138, 199, 100, 30, 16, 152, 131, 255, 10, 4, 180, 19, 232, 23, 218, 221, 78, 218, 102, 164, 188, 167, 62, 117, 3, 178, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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