Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83444f76a0a3a953fcadef07da694678627d33e6715efb47c1cd85d2776338f8

Tx prefix hash: bc1fd5a65122c4ceaa1fce1ec64d8b8bea2f0682f90d2f750ef7225de238fa42
Tx public key: bfa0f5c26c34083319ce9a825d4f06103b15421a97281da477b5a784b9c69050
Timestamp: 1702471778 Timestamp [UCT]: 2023-12-13 12:49:38 Age [y:d:h:m:s]: 01:167:14:15:47
Block: 912255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380945 RingCT/type: yes/0
Extra: 01bfa0f5c26c34083319ce9a825d4f06103b15421a97281da477b5a784b9c69050021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35cadafb5a0458f1f2eaa796dd8fe9e218fbb9663cc1728dc52330b2d45734f1 0.600000000000 1369481 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": 912265, "vin": [ { "gen": { "height": 912255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35cadafb5a0458f1f2eaa796dd8fe9e218fbb9663cc1728dc52330b2d45734f1" } } ], "extra": [ 1, 191, 160, 245, 194, 108, 52, 8, 51, 25, 206, 154, 130, 93, 79, 6, 16, 59, 21, 66, 26, 151, 40, 29, 164, 119, 181, 167, 132, 185, 198, 144, 80, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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