Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbab0a739bebb0857d3d666023c07f564c84695f41a1378b0710de1da3c21a1e

Tx prefix hash: cd7e2b059a1e1d6f3f29ea248865989f3332dfb4da405b93bc8d63c9b35c65bb
Tx public key: 1ec4972e3c38a6d4c9ac6f80dca757ff51ce10a75070ceb55555e550b366a0ba
Timestamp: 1728915683 Timestamp [UCT]: 2024-10-14 14:21:23 Age [y:d:h:m:s]: 01:025:20:10:19
Block: 1131475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276830 RingCT/type: yes/0
Extra: 011ec4972e3c38a6d4c9ac6f80dca757ff51ce10a75070ceb55555e550b366a0ba021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c004548d2c6ea4a3260812e6379ddd15f74e48a2b1be1c78bd1285bc170e0e7 0.600000000000 1614378 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": 1131485, "vin": [ { "gen": { "height": 1131475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c004548d2c6ea4a3260812e6379ddd15f74e48a2b1be1c78bd1285bc170e0e7" } } ], "extra": [ 1, 30, 196, 151, 46, 60, 56, 166, 212, 201, 172, 111, 128, 220, 167, 87, 255, 81, 206, 16, 167, 80, 112, 206, 181, 85, 85, 229, 80, 179, 102, 160, 186, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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