Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c76642e4ec692a40218bb095fd859343b8b11fa79d4aa2b27dd7f15820c1267e

Tx prefix hash: 13e53a3f45ee6ba0e633080df99d3069596556b150a663bba6ca07a10ce735d7
Tx public key: f9d851ae4d0d33af70793dc9f733fab01b1454237edafc87f6419af5589f234b
Timestamp: 1724527295 Timestamp [UCT]: 2024-08-24 19:21:35 Age [y:d:h:m:s]: 00:226:06:39:27
Block: 1095102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161557 RingCT/type: yes/0
Extra: 01f9d851ae4d0d33af70793dc9f733fab01b1454237edafc87f6419af5589f234b021100000001e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e230278a1c70a730e759cf7dd5eaa09f2d1bf4cf43b7a70377b0d75d946224f8 0.600000000000 1570243 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": 1095112, "vin": [ { "gen": { "height": 1095102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e230278a1c70a730e759cf7dd5eaa09f2d1bf4cf43b7a70377b0d75d946224f8" } } ], "extra": [ 1, 249, 216, 81, 174, 77, 13, 51, 175, 112, 121, 61, 201, 247, 51, 250, 176, 27, 20, 84, 35, 126, 218, 252, 135, 246, 65, 154, 245, 88, 159, 35, 75, 2, 17, 0, 0, 0, 1, 227, 55, 53, 142, 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