Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc4e2b21bd99ee9e57bf208046d54496e14afd4cb1d2a2802d43e2cd4e44f08a

Tx prefix hash: b9c6fce5d676d835420966c98e9fc2fc3395cc9bf990b8893be73be7943bae30
Tx public key: 1cf59cf84a602ea1ba5e13f99b91e99c0cc9ae923d9d9a8dccb7f8dcda4c56c2
Timestamp: 1726927216 Timestamp [UCT]: 2024-09-21 14:00:16 Age [y:d:h:m:s]: 00:174:02:01:58
Block: 1114987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124245 RingCT/type: yes/0
Extra: 011cf59cf84a602ea1ba5e13f99b91e99c0cc9ae923d9d9a8dccb7f8dcda4c56c2021100000005144294a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8b69504efa4ba45d8f167d0d372d2518979a2d3034e473326175c156d45963d 0.600000000000 1594960 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": 1114997, "vin": [ { "gen": { "height": 1114987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8b69504efa4ba45d8f167d0d372d2518979a2d3034e473326175c156d45963d" } } ], "extra": [ 1, 28, 245, 156, 248, 74, 96, 46, 161, 186, 94, 19, 249, 155, 145, 233, 156, 12, 201, 174, 146, 61, 157, 154, 141, 204, 183, 248, 220, 218, 76, 86, 194, 2, 17, 0, 0, 0, 5, 20, 66, 148, 160, 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