Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cd154c0746963250210aed8300796910a1401629c91f4e9955fdb0d2da05784

Tx prefix hash: 8bc238e0e09559b0f75736a66ec1f30ccf1aac193c25ae3b528eabb98a6eee8e
Tx public key: f86ce6b4ba64ac18aa4c6d30772d0cd1108e31a678bd0585ecd8d0ae75b424f5
Timestamp: 1710775913 Timestamp [UCT]: 2024-03-18 15:31:53 Age [y:d:h:m:s]: 01:072:02:36:08
Block: 981096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312546 RingCT/type: yes/0
Extra: 01f86ce6b4ba64ac18aa4c6d30772d0cd1108e31a678bd0585ecd8d0ae75b424f502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25237f9aefcd42a2d2a3b4fd00407e160cef53d00524f256b2f343909ac375c0 0.600000000000 1441189 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": 981106, "vin": [ { "gen": { "height": 981096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25237f9aefcd42a2d2a3b4fd00407e160cef53d00524f256b2f343909ac375c0" } } ], "extra": [ 1, 248, 108, 230, 180, 186, 100, 172, 24, 170, 76, 109, 48, 119, 45, 12, 209, 16, 142, 49, 166, 120, 189, 5, 133, 236, 216, 208, 174, 117, 180, 36, 245, 2, 17, 0, 0, 0, 3, 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