Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c114205eb9b1934d8a2f9278aec940960a85d50610a4b2a4d682a92b20ede68e

Tx prefix hash: 571f0674eff3351b9d75de7718cefe58845d216894ee33dc623db8f9f13d8d72
Tx public key: 5c2791f28eb460b8a93a9a109b703e0b6b10f0ba2745b2482e20bac743372565
Timestamp: 1717605835 Timestamp [UCT]: 2024-06-05 16:43:55 Age [y:d:h:m:s]: 00:284:19:44:56
Block: 1037708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203561 RingCT/type: yes/0
Extra: 015c2791f28eb460b8a93a9a109b703e0b6b10f0ba2745b2482e20bac74337256502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed69dbef0ae260910a7a5eb6f4a2eb3f046fbf8e186efd5f9854d57e134d0cbe 0.600000000000 1506261 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": 1037718, "vin": [ { "gen": { "height": 1037708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed69dbef0ae260910a7a5eb6f4a2eb3f046fbf8e186efd5f9854d57e134d0cbe" } } ], "extra": [ 1, 92, 39, 145, 242, 142, 180, 96, 184, 169, 58, 154, 16, 155, 112, 62, 11, 107, 16, 240, 186, 39, 69, 178, 72, 46, 32, 186, 199, 67, 55, 37, 101, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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