Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cfb28598a9df5d6c14fdba9b1df10d2c30b011e191467f835308f6cd5935e4e

Tx prefix hash: 637ef4413ca80a27f025c3d1e25ce15b48f78dcf36b0831b8ba33c2670bb6b79
Tx public key: b3f95de25bbc54c4f3a23d20ee76164f18184dbd2ec8c9a6d607be45e8c31ec8
Timestamp: 1687555104 Timestamp [UCT]: 2023-06-23 21:18:24 Age [y:d:h:m:s]: 01:289:10:25:58
Block: 788828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468005 RingCT/type: yes/0
Extra: 01b3f95de25bbc54c4f3a23d20ee76164f18184dbd2ec8c9a6d607be45e8c31ec80211000000024b8f5122000000000000000000

1 output(s) for total of 1.493776161000 dcy

stealth address amount amount idx
00: 061dcc9e9d1a4e9f2cedf2b42de0e9bb1113b71e9ac7fdf1943710ff2e105970 1.493776161000 1238985 of 0

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": 788838, "vin": [ { "gen": { "height": 788828 } } ], "vout": [ { "amount": 1493776161, "target": { "key": "061dcc9e9d1a4e9f2cedf2b42de0e9bb1113b71e9ac7fdf1943710ff2e105970" } } ], "extra": [ 1, 179, 249, 93, 226, 91, 188, 84, 196, 243, 162, 61, 32, 238, 118, 22, 79, 24, 24, 77, 189, 46, 200, 201, 166, 214, 7, 190, 69, 232, 195, 30, 200, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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