Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4d779b0e4b32800b7ba6dd1e705e34fb023ecd289a48937e260fb81fd2b9f3f

Tx prefix hash: 83e04e6dfb41d17094a5663cbfef437a4a92acc5a0a1b7fff45c8416c140cf64
Tx public key: f7801b4930ab940d5aa5381df1f83d2eb23b59bb593ebf3615fcf91dfeaa6744
Timestamp: 1734125332 Timestamp [UCT]: 2024-12-13 21:28:52 Age [y:d:h:m:s]: 00:101:12:15:32
Block: 1174566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72321 RingCT/type: yes/0
Extra: 01f7801b4930ab940d5aa5381df1f83d2eb23b59bb593ebf3615fcf91dfeaa67440211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b37dce4a8eafd8f402fb84efbd86f2f599a9b946efda7507bf535a8337f8cb51 0.600000000000 1660733 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": 1174576, "vin": [ { "gen": { "height": 1174566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b37dce4a8eafd8f402fb84efbd86f2f599a9b946efda7507bf535a8337f8cb51" } } ], "extra": [ 1, 247, 128, 27, 73, 48, 171, 148, 13, 90, 165, 56, 29, 241, 248, 61, 46, 178, 59, 89, 187, 89, 62, 191, 54, 21, 252, 249, 29, 254, 170, 103, 68, 2, 17, 0, 0, 0, 2, 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