Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff5833a8a066e3a4bbd6ba714c3401b9fa6f333af1a94536b0a239bca2080a90

Tx prefix hash: a1462d955c8f78b0e639878b9d33118be8e47256b5e213cb016235d6eea4f385
Tx public key: 1c19c0765424865981082fd7bcd1906a55f3ea4b9171d8869d36512a1b83a94d
Timestamp: 1714960659 Timestamp [UCT]: 2024-05-06 01:57:39 Age [y:d:h:m:s]: 00:356:14:52:19
Block: 1015773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254936 RingCT/type: yes/0
Extra: 011c19c0765424865981082fd7bcd1906a55f3ea4b9171d8869d36512a1b83a94d02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2e5022f4c533cf6f6580435744f1e5c521a3a383457f8354da011ebe018363e 0.600000000000 1479216 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": 1015783, "vin": [ { "gen": { "height": 1015773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2e5022f4c533cf6f6580435744f1e5c521a3a383457f8354da011ebe018363e" } } ], "extra": [ 1, 28, 25, 192, 118, 84, 36, 134, 89, 129, 8, 47, 215, 188, 209, 144, 106, 85, 243, 234, 75, 145, 113, 216, 134, 157, 54, 81, 42, 27, 131, 169, 77, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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