Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c07b7a61050f17ed16abe5378482577504b3a6887a2b14eb3842e5c4ce77edbb

Tx prefix hash: 1676c3f7f7d7f6b1346052da2a30a0834ba5133e42ec3e0a3367410d15a29704
Tx public key: 63901628cc2aaea08c443938425b2907b2ff8628e6e0b2c0479cb8979c7ac1b3
Timestamp: 1720233088 Timestamp [UCT]: 2024-07-06 02:31:28 Age [y:d:h:m:s]: 00:276:21:06:30
Block: 1059478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197831 RingCT/type: yes/0
Extra: 0163901628cc2aaea08c443938425b2907b2ff8628e6e0b2c0479cb8979c7ac1b30211000000028fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfdb8551842d6a3b4485f3bd06e04c52fe5a388cc23cac1ba6adea200455795a 0.600000000000 1529947 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": 1059488, "vin": [ { "gen": { "height": 1059478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfdb8551842d6a3b4485f3bd06e04c52fe5a388cc23cac1ba6adea200455795a" } } ], "extra": [ 1, 99, 144, 22, 40, 204, 42, 174, 160, 140, 68, 57, 56, 66, 91, 41, 7, 178, 255, 134, 40, 230, 224, 178, 192, 71, 156, 184, 151, 156, 122, 193, 179, 2, 17, 0, 0, 0, 2, 143, 218, 155, 45, 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