Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83acd7fb0fe5807d8fb413245975cdc3cb438e782dba23ca7178a60c1c908c84

Tx prefix hash: 7c819ecba7a43cf9b62aa7a5cdd0f78e542a7fe0a97c80ae44bb07d98f19c98b
Tx public key: 8b1373fde1f33b6ef356ee229302f63b73d6f61f2780acef892aa050e2803693
Timestamp: 1726134791 Timestamp [UCT]: 2024-09-12 09:53:11 Age [y:d:h:m:s]: 00:276:18:08:07
Block: 1108413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197580 RingCT/type: yes/0
Extra: 018b1373fde1f33b6ef356ee229302f63b73d6f61f2780acef892aa050e280369302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13ca0293778a1c11ea8c6bbdbc885624e9fb57e6ca2904eaff2f8d37e818bf87 0.600000000000 1586300 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": 1108423, "vin": [ { "gen": { "height": 1108413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13ca0293778a1c11ea8c6bbdbc885624e9fb57e6ca2904eaff2f8d37e818bf87" } } ], "extra": [ 1, 139, 19, 115, 253, 225, 243, 59, 110, 243, 86, 238, 34, 147, 2, 246, 59, 115, 214, 246, 31, 39, 128, 172, 239, 137, 42, 160, 80, 226, 128, 54, 147, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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