Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc62999db2b0901ab03375f0cf47cff382423cb15afe3f30b91de9679e7c649d

Tx prefix hash: ad1e6694b20c3684ab886f3c7ce7bd25ed729ef52c852d04d9be5dd3cf98bb9b
Tx public key: 0020ad68d8eb1984e55d8adcd8a800b0bd6def0df234bd654e3e8ec80160b9a4
Timestamp: 1719323659 Timestamp [UCT]: 2024-06-25 13:54:19 Age [y:d:h:m:s]: 01:141:05:32:25
Block: 1051939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359490 RingCT/type: yes/0
Extra: 010020ad68d8eb1984e55d8adcd8a800b0bd6def0df234bd654e3e8ec80160b9a402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3295fb17d194911a0ba809a68b3d66fe15818ccfe8a7860b3dd785e9fc4dc429 0.600000000000 1522260 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": 1051949, "vin": [ { "gen": { "height": 1051939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3295fb17d194911a0ba809a68b3d66fe15818ccfe8a7860b3dd785e9fc4dc429" } } ], "extra": [ 1, 0, 32, 173, 104, 216, 235, 25, 132, 229, 93, 138, 220, 216, 168, 0, 176, 189, 109, 239, 13, 242, 52, 189, 101, 78, 62, 142, 200, 1, 96, 185, 164, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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