Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b08ca3b8c766cdf939edd8d2fac1c8aa34e6790fa6499d7ce50f79f7c52cfbe9

Tx prefix hash: e5d9a91982fbc211b199774a25999e2b69d5b1ce373a024f1ed8d741c5307746
Tx public key: 747c31843af546d1577bf102118a9a0e7554b09e3ae7267c5b76c8ee7fca7238
Timestamp: 1756772776 Timestamp [UCT]: 2025-09-02 00:26:16 Age [y:d:h:m:s]: 00:146:10:33:54
Block: 1359451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104530 RingCT/type: yes/0
Extra: 01747c31843af546d1577bf102118a9a0e7554b09e3ae7267c5b76c8ee7fca723802110000000aad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5af762587c8d73cae8be84894fe5e8d908fad4b224c93f9029fdef45fe9714ee 0.600000000000 1847464 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": 1359461, "vin": [ { "gen": { "height": 1359451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5af762587c8d73cae8be84894fe5e8d908fad4b224c93f9029fdef45fe9714ee" } } ], "extra": [ 1, 116, 124, 49, 132, 58, 245, 70, 209, 87, 123, 241, 2, 17, 138, 154, 14, 117, 84, 176, 158, 58, 231, 38, 124, 91, 118, 200, 238, 127, 202, 114, 56, 2, 17, 0, 0, 0, 10, 173, 121, 72, 208, 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