Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c1d4905db5631beeb729078199afe8fb8f2aac9f195987d7ebeb8e28946b125

Tx prefix hash: b6b180402581dfb0a20f498424086c37ac689edbb727588facbfea599aa5fed5
Tx public key: 432c1e869add551d49dfb2320c35089999e082f317f73034e6eded6a861a0232
Timestamp: 1698366822 Timestamp [UCT]: 2023-10-27 00:33:42 Age [y:d:h:m:s]: 01:087:03:24:55
Block: 878431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323450 RingCT/type: yes/0
Extra: 01432c1e869add551d49dfb2320c35089999e082f317f73034e6eded6a861a023202110000000fe6d27f9c000000000000000000

1 output(s) for total of 0.754038391000 dcy

stealth address amount amount idx
00: 784b0f8282c83333f34c9ab97770fbae30c0f81647ac566ed368d72d2c70f373 0.754038391000 1333873 of 0

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": 878441, "vin": [ { "gen": { "height": 878431 } } ], "vout": [ { "amount": 754038391, "target": { "key": "784b0f8282c83333f34c9ab97770fbae30c0f81647ac566ed368d72d2c70f373" } } ], "extra": [ 1, 67, 44, 30, 134, 154, 221, 85, 29, 73, 223, 178, 50, 12, 53, 8, 153, 153, 224, 130, 243, 23, 247, 48, 52, 230, 237, 237, 106, 134, 26, 2, 50, 2, 17, 0, 0, 0, 15, 230, 210, 127, 156, 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