Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a84ec2218d6f92ec0ea2e6cdbc6b0efd6c301626799f11613d906ddcc096b3a

Tx prefix hash: 8590a6cf65197dbda3fdbbb2e233790c919b222346b0bdc0d42ac7726a63df50
Tx public key: b1361ecf8e62f58f4a10af928ccddefaefd6d0f5587840c61702f8ac7291d83f
Timestamp: 1735211919 Timestamp [UCT]: 2024-12-26 11:18:39 Age [y:d:h:m:s]: 00:089:13:05:02
Block: 1183553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63759 RingCT/type: yes/0
Extra: 01b1361ecf8e62f58f4a10af928ccddefaefd6d0f5587840c61702f8ac7291d83f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a894c6851f1419f5e9ca921dc3eeda793c3ab02f8bbe24b16da10a8fa7ac3579 0.600000000000 1669998 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": 1183563, "vin": [ { "gen": { "height": 1183553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a894c6851f1419f5e9ca921dc3eeda793c3ab02f8bbe24b16da10a8fa7ac3579" } } ], "extra": [ 1, 177, 54, 30, 207, 142, 98, 245, 143, 74, 16, 175, 146, 140, 205, 222, 250, 239, 214, 208, 245, 88, 120, 64, 198, 23, 2, 248, 172, 114, 145, 216, 63, 2, 17, 0, 0, 0, 1, 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