Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 609a88ce18b82af2ab2dcdf41fb8749f7efa36d72151beeb245f3640a79ce902

Tx prefix hash: 0c12c1bab9515fb46c1ccd49f4589ab702ff9a25b8f90ffa1453b93ee6614dad
Tx public key: 666f3a9c075516050fe8c151f61c80d8afbc54d09749b0debcde8ca0a4c64691
Timestamp: 1715114699 Timestamp [UCT]: 2024-05-07 20:44:59 Age [y:d:h:m:s]: 01:196:21:09:25
Block: 1017060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399338 RingCT/type: yes/0
Extra: 01666f3a9c075516050fe8c151f61c80d8afbc54d09749b0debcde8ca0a4c6469102110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30abd9ae8ee345d326c40fab460f9c907a749bcaf0a934f5e41ba1afe301e3f1 0.600000000000 1480823 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": 1017070, "vin": [ { "gen": { "height": 1017060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30abd9ae8ee345d326c40fab460f9c907a749bcaf0a934f5e41ba1afe301e3f1" } } ], "extra": [ 1, 102, 111, 58, 156, 7, 85, 22, 5, 15, 232, 193, 81, 246, 28, 128, 216, 175, 188, 84, 208, 151, 73, 176, 222, 188, 222, 140, 160, 164, 198, 70, 145, 2, 17, 0, 0, 0, 14, 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