Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1fcf8adadac92f85992729ec82f9d5cc16860b4c6661271360dfb9d05febde1

Tx prefix hash: 4480954cf3a58dee43832c73c236e037f1c311a74ac7bdd1302a1d2b014a8022
Tx public key: 57a6c3f2e3c3569811fac5254dae426e10399c315d4486bc4fbceac4e550ab22
Timestamp: 1731916955 Timestamp [UCT]: 2024-11-18 08:02:35 Age [y:d:h:m:s]: 01:001:07:03:03
Block: 1156256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259343 RingCT/type: yes/0
Extra: 0157a6c3f2e3c3569811fac5254dae426e10399c315d4486bc4fbceac4e550ab22021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6071158b4e8c0f83ffe5327a4fd56f62d1fa3d6df79241ec1c993cc03a963ecb 0.600000000000 1641879 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": 1156266, "vin": [ { "gen": { "height": 1156256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6071158b4e8c0f83ffe5327a4fd56f62d1fa3d6df79241ec1c993cc03a963ecb" } } ], "extra": [ 1, 87, 166, 195, 242, 227, 195, 86, 152, 17, 250, 197, 37, 77, 174, 66, 110, 16, 57, 156, 49, 93, 68, 134, 188, 79, 188, 234, 196, 229, 80, 171, 34, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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