Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42d6e570d974bd374e5c8adfb23d4018a1e1c9308928f08e4861988fffa0eaac

Tx prefix hash: 2bc730fd992f8449dadee2b9253599b1b5a2e1f6fb0ea8c2fba2bda9ba72962d
Tx public key: 06e5b0e9418e1702d44bf2e0fafac1cdf25c6b5a3a99666090ed1ce60d2aedcd
Timestamp: 1706863164 Timestamp [UCT]: 2024-02-02 08:39:24 Age [y:d:h:m:s]: 01:061:17:15:28
Block: 948635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305162 RingCT/type: yes/0
Extra: 0106e5b0e9418e1702d44bf2e0fafac1cdf25c6b5a3a99666090ed1ce60d2aedcd02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d44419978e9548b1c724c7ef27e509477b38faca9cdb6a02decd957a1f3984d 0.600000000000 1407083 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": 948645, "vin": [ { "gen": { "height": 948635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d44419978e9548b1c724c7ef27e509477b38faca9cdb6a02decd957a1f3984d" } } ], "extra": [ 1, 6, 229, 176, 233, 65, 142, 23, 2, 212, 75, 242, 224, 250, 250, 193, 205, 242, 92, 107, 90, 58, 153, 102, 96, 144, 237, 28, 230, 13, 42, 237, 205, 2, 17, 0, 0, 0, 7, 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