Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2827b5a3f002cc48dfa39be8423f0ae2441f945d7990e51fc4589ebdc57a320f

Tx prefix hash: 29d8e5b916716f704fad232cee2c419c86fb94d6528df184011426323a090968
Tx public key: b6c65500803ba8b9fd439611fdf8ae4510883e81aaec9da2d5aa47f642bfda15
Timestamp: 1729444346 Timestamp [UCT]: 2024-10-20 17:12:26 Age [y:d:h:m:s]: 00:239:05:32:24
Block: 1135847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170694 RingCT/type: yes/0
Extra: 01b6c65500803ba8b9fd439611fdf8ae4510883e81aaec9da2d5aa47f642bfda150211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f77f002229af2b29ec633ac4b9fcb48a1378b6bc5300935f87b7f41574e6d730 0.600000000000 1619186 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": 1135857, "vin": [ { "gen": { "height": 1135847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f77f002229af2b29ec633ac4b9fcb48a1378b6bc5300935f87b7f41574e6d730" } } ], "extra": [ 1, 182, 198, 85, 0, 128, 59, 168, 185, 253, 67, 150, 17, 253, 248, 174, 69, 16, 136, 62, 129, 170, 236, 157, 162, 213, 170, 71, 246, 66, 191, 218, 21, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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