Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8066dc93559e739d4c0dcc14380b83634b510208c0f09f6baf34ca3ae3729d3b

Tx prefix hash: af971ecaecc93c29f80309d2bd4136a8ac7eaf48054798354668f1bdde5f711a
Tx public key: 5e38a0fe6ec00c20e33b31fd7b36c99aa1ede9bf71f6a44bab1d72244494ee0a
Timestamp: 1722623428 Timestamp [UCT]: 2024-08-02 18:30:28 Age [y:d:h:m:s]: 00:298:00:18:23
Block: 1079303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212923 RingCT/type: yes/0
Extra: 015e38a0fe6ec00c20e33b31fd7b36c99aa1ede9bf71f6a44bab1d72244494ee0a02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45aa4244ecc1a76f9025abb16a18e340b15b325a8d732bab285596a97802b48e 0.600000000000 1552204 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": 1079313, "vin": [ { "gen": { "height": 1079303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45aa4244ecc1a76f9025abb16a18e340b15b325a8d732bab285596a97802b48e" } } ], "extra": [ 1, 94, 56, 160, 254, 110, 192, 12, 32, 227, 59, 49, 253, 123, 54, 201, 154, 161, 237, 233, 191, 113, 246, 164, 75, 171, 29, 114, 36, 68, 148, 238, 10, 2, 17, 0, 0, 0, 2, 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